When running the GenWIP program in a batch process, the DAT and POL files that appear in the WIP directory follow the 8.3 file name convention.
In Documaker Desktop, when you save a transaction to WIP the system checks the WIPData control group for the WIP database file name and path. If the system finds the WIP.DBF file, it uses the existing database file name convention.
If the WIP.DBF file is not present, the system checks the WIPData control group and looks for WIPDFDFile option. This option is not required, but you can use it to specify the full path and name for the WIP DFD file. By default the system uses the WIPData control group file and path.
If the system finds the WIP.DFD file, the system checks for an entry for the INT_Length field in the FormSetID control group and Documaker Desktop uses that convention.
For example, the WIP.DFD file name length below is set to 8 in the WIP.DFD file:
[Fields]
FieldName=FORMSETID
[Field:FormSetID]
EXT_Length = 8
INT_Length = 8
If the system does not find a WIP.DBF or WIP.DFD file, the system uses internal settings to create DAT and POL files using a GUID 32-bit file name.
The WIP.DBF is created and that database is used by Documaker Desktop.
For WIP, the system can store the index, but not the data. We have tested using the AFEMAIN program to store a WIP index in MS SQL and on Oracle ODBC version 8.01.71.00 on Windows 2000 to save the WIP table to Oracle 8i Enterprise Edition Release 8.1.6.0.0 on a Sun OS 5.7 Oracle database.
© Copyright 2018, Oracle and/or its affiliates. All rights reserved. Legal notices.